Typhoon Ma-on (2004)
This article's lead section may be too short to adequately summarize the key points. (November 2023) |
Meteorological history | |
---|---|
Formed | October 3, 2004 |
Dissipated | October 10, 2004 |
Very strong typhoon | |
10-minute sustained (JMA) | |
Highest winds | 185 km/h (115 mph) |
Lowest pressure | 920 hPa (mbar); 27.17 inHg |
Category 5-equivalent super typhoon | |
1-minute sustained (SSHWS/JTWC) | |
Highest winds | 260 km/h (160 mph) |
Lowest pressure | 898 hPa (mbar); 26.52 inHg |
Overall effects | |
Fatalities | 7 |
Missing | 2 |
Damage | $623 million (2004 USD) |
Areas affected | Japan, Alaska |
IBTrACS | |
Part of the 2004 Pacific typhoon season |
Typhoon Ma-on, known in the Philippines as Typhoon Rolly, was a powerful typhoon that produced record breaking wind gusts across the Tokyo Metropolitan Area during October 2004. The twenty-second named storm of the 2004 Pacific typhoon season, Ma-on was the second of three consecutive storms to hit Japan during the period between late-September to mid-October 2004.
Meteorological history
[edit]Typhoon Ma-on originated from a weak low-pressure area accompanied by persistent convection, or thunderstorms, north-northwest of Guam on September 29, 2004. Though environmental conditions featured weak wind shear and modest diffluence, favoring tropical cyclogenesis, the convection was cyclical and the system did not develop much over the following two days. Over the first three days of October, organization fluctuated as semi-persistent convection appeared over the circulation center. On October 3, a QuikScat satellite pass revealed a well-developed circulation while a ship 555 km (345 mi) south of the low reported 45 km/h (28 mph) winds.[1] The Japan Meteorological Agency (JMA) began monitoring the low as a tropical depression at 06:00 UTC.[2] Twelve hours later, the depression crossed 135°E and entered the Philippine Atmospheric, Geophysical and Astronomical Services Administration's (PAGASA) area of responsibility, receiving the local name Rolly from the agency.[1] Becoming nearly stationary, the system turned due north late on October 3. At 00:00 UTC on October 4, the Joint Typhoon Warning Center (JTWC) classified the system as Tropical Depression 26W; the newly designated cyclone was situated over the Philippine Sea roughly 1,145 km (711 mi) west-northwest of Guam at this time.[3] Six hours later, both the JMA and JTWC analyzed the depression and concluded it had become a tropical storm; the JMA assigning it the name Ma-on.[1][2][3] Slow organization of Ma-on ensued over the following two days as it moved north and later northwest along the edge of a high-pressure area.[1] The JTWC estimated Ma-on to have reached typhoon status around 06:00 UTC on October 6,[3] with the JMA following suit 12 hours later.[2]
Synoptic patterns changed dramatically on October 7 as a trough emerged off the coast of East China and prompted Ma-on to turn northeast. Simultaneously, it provided a greatly enhanced poleward outflow channel toward Japan. The shift in motion was also accompanied by a period of rapid intensification, with a well-defined eye forming.[1] Over the 24 hour-period from 18:00 to 18:00 UTC October 6–7, Ma-on's barometric pressure dropped from 965 mb (hPa; 28.50 inHg) to 920 mb (hPa; 27.17 inHg). The end of this phase marked the peak intensity of the typhoon, with winds reaching 185 km/h (115 mph).[2] The JTWC estimated Ma-on to have been a significantly stronger storm with one-minute sustained winds topping out at 260 km/h (160 mph) at 00:00 UTC on October 8. This ranked it as a Category 5-equivalent typhoon on the Saffir–Simpson hurricane wind scale. They also assessed the pressure to have decreased to 898 mb (hPa; 26.52 inHg).[3] Not long after reaching this intensity, Ma-on's eye began to shrink and become ragged. Acceleration to the northeast, with its forward speed reaching 54 km/h (34 mph), ensued throughout the day and weakening ensued. Convection became increasingly asymmetric with dry air impinging on the southwestern semicircle, indicating the beginning of extratropical transition. The typhoon made landfall along the Izu Peninsula of Japan around 07:00 UTC on October 9, with winds of 150 km/h (93 mph) and a central pressure of 950 mb (hPa; 28.06 inHg).[1][2] The JTWC estimated Ma-on to have been a Category 3-equivalent with one-minute sustained winds of 195 km/h (121 mph).[3] Roughly six hours after striking Japan, the rapidly weakening typhoon re-emerged over the Pacific Ocean. The system completed its extratropical transition later on October 9 as it weakened below typhoon intensity.[1][2]
After losing a defined low-level circulation early on October 10,[2] Ma-on's the remnant trough continued eastward across the North Pacific. More than a week later, by October 18, the storm moved over the Bering Sea and began to intensify rapidly as conditions favored bombogenesis of the baroclinic system.[4] It is not certain whether this system was predominantly the remnants of Ma-on or another non-tropical system which had its origins near Norway and traversed Eurasia.[5] Regardless of its dominant origin the storm moved across the central Aleutian Islands with a pressure of 978 mb (hPa; 28.88 inHg) on October 17 and doubled back to the west throughout the next day. As it moved over the Gulf of Anadyr, it quickly deepened to an exceptionally powerful 941 mb (hPa; 27.79 inHg). The intensification resulted from the influx of warm, moist air directly associated with the remnants of Ma-on combining with cold air from an upper-level low over the Russian Far East being entrained into the southeastern portion of the circulation. Winds up to typhoon-force occurred over a large swath of the Bering Sea and portions of western coastal Alaska. Situated 640 km (400 mi) west of Nome, Alaska, the powerful storm subsequently weakened and slowed on October 19. By October 20, the system filled to 980 mb (hPa; 28.95 inHg) low and reached a position 640 km (400 mi) west of Kotzebue, Alaska.[6] Over the subsequent four days, the low meandered in the same general area and was last noted on October 24.[7]
Preparations, impact and aftermath
[edit]Japan
[edit]As Typhoon Ma-on began turning to the north on October 8 towards Japan, the JMA warned residents in the Tōkai, Kansai, and Shikoku regions of heavy rain.[8] Meteorologists warned it would likely become the strongest storm to strike the Kantō region in at least a decade.[9] Japan Airlines and All Nippon Airways cancelled 262 flights collectively on October 9, affecting 53,000 passengers.[10] Overall, 380 domestic and 72 international flights were cancelled because of Ma-on.[11] The Central Japan Railway Company temporarily suspended service for the entire Tōkaidō Shinkansen line, which travels from Tokyo to Shin-Ōsaka. Mandatory evacuation orders were issued for 3,528 families across five prefectures, while a further 1,600 families voluntarily evacuated from 13 others.[10] Voluntary evacuations also took place on Minamidaitōjima.[12] Practice and qualifying runs for the 2004 Japanese Grand Prix at the Suzuka Circuit, initially scheduled for October 9, were suspended until the following day.[13] Play at the Japan Open was suspended briefly because of the rain from the storm.[14]
Typhoon Ma-on was the eighth of a record-breaking ten landfalling typhoons in Japan during the 2004 season.[15] Of these storms, Ma-on was the only system to strike eastern areas of the nation directly and the second-strongest, with a landfall pressure of 950 mb (hPa; 28.06 inHg).[16][17] Collectively, these storms resulted in 214 fatalities and over 2,000 injuries. Widespread and extensive damage to housing and infrastructure occurred with well over 200,000 homes damaged or destroyed and financial losses in excess of ¥564 billion (US$5 billion).[16]
The typhoon produced record-breaking wind across the Izu Peninsula when it made landfall on October 9.[1] The most intense winds of more than 215 km/h (134 mph) were confined to areas along Sagami Bay, about 40 km (25 mi) southeast of Tokyo. Contrary to most tropical cyclones, which see their strongest winds in the right-front quadrant, these winds occurred along the backside of Typhoon Ma-on. As the storm passed through, a low level jet formed along the east edge of the Kanto Mountains and facilitated an extreme gap flow event.[15][18] A peak gust of 243 km/h (151 mph) was measured in Irōzaki; sustained values reached 142 km/h (88 mph) in Ajiro. Record high gusts were observed in Irōzaki, Ajiro, and Ojima, while record high sustained winds occurred in Ajiro, Haneda, and Ojima.[1] The extreme gap flow event resulted from the warm air associated with Ma-on moving over the relatively cool air over the Kanto Plain. As the backside of the storm moved through, northerly winds pushed the cooler air south and allowed it to extend to higher altitudes as it paralleled the mountains along the west side of the plains. Model simulations of the event indicated that without the mountains, winds would have been no more than 126 km/h (78 mph) in the same areas.[15]
Torrential rains accompanied the storm, with several areas reporting rainfall rates in excess of 60 mm (2.4 in) per hour. A local record of 89 mm (3.5 in) per hour was measured in Omaezaki, Shizuoka, which contributed to a 24-hour record of 360 mm (14 in) at the same station. Storm total values peaked in Omaezaki at 413 mm (16.3 in) over a three-day period;[1] measurements in excess of 300 mm (12 in) were confined to Aichi, Chiba, Kanagawa, Shizuoka, and Yamanashi prefectures. Enhanced precipitation affected areas well to the west of Ma-on, such as in Okinawa Prefecture where up to 190 mm (7.5 in) fell in Motobu.[19]
Landslides triggered by the heavy rains caused widespread disruptions in the nation as well as one fatality in Kamakura, Kanagawa.[20] Chiba and Kanagawa Prefectures were particularly hard-hit. Nearly 500 collective landslides affected the prefectures, damaging homes and paralyzing traffic.[20][21] Part of National Route 19 was blocked and two buildings were damaged by a slide in Nagano Prefecture.[22] A landslide in Niisato, Iwate, blocked portions of a road and prompted voluntary evacuations.[23] Two landslides and flooding caused a few road closures in Miyagi Prefecture.[24] Slides occurred as far west as Nara and Okinawa. One shut down a 2 km (1.2 mi) stretch of road in Hokkejicho while three occurred in Nago.[12][25]
Approximately 180,000 Tokyo Electric customers lost power during the storm.[13] In Minamiizu, Shizuoka, a power pole struck a man downed by high winds and later died at the hospital.[11] Extensive agricultural and infrastructural damage occurred in Fukushima Prefecture, where losses amounted to ¥3.4 billion[26] Agricultural losses in Chiba amounted to ¥1.2 billion.[21]
Widespread disruptions to rail service in eastern Japan resulted from the typhoon. Service along the Tokyo Metro Namboku Line subway suspended due to flooding at the Azabu-Jūban Station. Flooding and heavy rains prompted suspensions of the Saikyō, Keiyō, Tōhoku Shinkansen, Jōetsu Shinkansen, Nagano Shinkansen, and Keihin-Tōhoku lines. Trains along the Tokyo Monorail and express lines from the Odakyu Electric Railway and Keikyu were also interrupted. Additionally, a landslide struck a portion of the Chūō Main Line.[11] A train derailed in Yamanashi Prefecture due to debris on the track.[27]
In Gunma Prefecture a man was injured after being blown off his roof in Ōta while trying to repair a gutter. A few homes were flooded and damage in the prefecture amounted to ¥41.2 million.[28] One person sustained minor injuries in Tokorozawa. Flooding in Saitama Prefecture affected 1,562 homes, 159 severely, and hundreds of roads were left impassible. In Iwatsuki, the Ayase River overflowed its banks and prompted the evacuation of 74 people. Damage to agriculture and forestry amounted to ¥253.5 million.[29] Six people were injured, one seriously, in Ibaraki Prefecture, by high winds. Numerous landslides occurred, some of which blocked rivers and caused flooding; others blocked rail lines. A total of 191 homes were affected by floods, 53 of which sustained damage. In terms of agriculture, 4,606 ha (11,380 acres) of crops flooded and losses reached ¥866 million.[30]
A car carrying four people was swept away by a landslide in Fujikawa; however, the occupants were unharmed. Landslides and flooding caused numerous disruptions to transportation. Damage amounted to ¥1.5 billion in Yamanashi Prefecture.[31] Landslides and flooding caused extensive damage in Aichi Prefecture. Damage to agriculture and forestry amounted to ¥391 million.[32] Two people were killed and eighteen others were injured in Chiba Prefecture. Roughly 1,100 homes were affected by flooding, some of which sustained damage. Evacuations orders were issued for 1,703 households across 14 municipalities. Property and infrastructure sustained extensive damage in Shizuoka Prefecture. A total of 165 homes collapsed while 244 more were partially destroyed. Four people were killed and one hundred others were injured. Water and power utilities were severely affected, with losses exceeding ¥1 billion collectively.[33] In Tokyo Prefecture, on the island of Kōzu-shima, 48 homes were evacuated during the storm. Flooding affected over 1,000 homes in Tokyo former, with 24 structures being destroyed. In Kanagawa Prefecture, a landslide killed one person in Kamakura while 43 others were injured throughout the prefecture. Nearly 200 landslides across the prefecture shut down large stretches of highway and rail lines, paralyzing public transportation. More than 2,400 homes were affected by flooding, though only three were destroyed.[34]
Additional, though minor, damage occurred in Akita,[35] Aomori,[36] Gifu,[37] Mie,[38] Niigata,[39] Shimane,[40] Tochigi,[41] Wakayama,[42] and Yamagata prefectures.[43] According to the Fire and Disaster Management Agency (FDMA), 135 homes were destroyed while 4,796 sustained damage. Another report from Rika Nenpyo indicated far greater damage: 5,553 homes destroyed and 7,843 others damaged. Relative to the intensity of the storm, however, casualties were low with seven-nine fatalities and 169 injuries.[44] Total damage from the storm amounted to ¥68.6 billion (US$603 million).[45] Insurance payouts amounted to ¥27.2 billion (US$241 million) in the wake of the storm.[44]
Alaska
[edit]The powerful extratropical remnants of Ma-on resulted in extensive damage along the west coast of Alaska in mid-October. Winds of 80 to 129 km/h (50 to 80 mph) battered many towns and fueled a damaging storm surge. At the Red Dog mine, a measurement of a 183 km/h (114 mph) gust was noted by the observer; however, this value was pegged as questionable and the highest verified gust was 124 km/h (77 mph). Other notable measurements include 114 km/h (71 mph) at Tin City, 110 km/h (70 mph) in Skookum Pass and Savoonga, 97 km/h (60 mph) in Golovin, and 95 km/h (59 mph) in Nome. The greatest storm surge occurred in areas without measuring capabilities, though a peak of 3.0 to 3.7 m (10 to 12 ft) was estimated in Shishmaref and 2.4 to 3.0 m (8 to 10 ft) in Kivalina. Nome itself was affected by a 3.19 m (10.45 ft) surge while Diomede and Teller had estimated values of 1.8 to 2.4 m (6 to 8 ft).[6] Record high water rises occurred at Nome and Red Dog Dock, peaking at 4.12 and 3.2 m (13.5 and 10.5 ft) respectively. The value in Nome exceeded the previous record of 3.7 m (12 ft) in October 1992; however, the measurement at Red Dog Dock was surpassed just over two months later.[46] Little precipitation accompanied the system, with only Coldfoot reporting snow accumulations of 18 cm (7 in).[6]
Nome suffered the brunt of damage from the cyclone, with most structures along the coast sustaining damage.[47] Forty-five residents had to be evacuated at the height of the storm.[6] Front Street flooded entirely and resembled a "war zone" according to residents. Most buildings in the area had their windows blown out from high winds except for those boarded with plywood. Some businesses had up to 0.91 m (3 ft) of water in their basement. Valves on three 450 kg (1,000 lb) propane tanks broke off during the storm at businesses on Front Street, prompting police to evacuate the area and the adjacent streets. Power was cut as a precautionary measure because of flammable gas.[47] Strong winds in Wales caused a 300-gallon fuel spill when a metal support at the village clinic toppled, rupturing the fuel line.[6] Large waves caused havoc across the Seward Peninsula. Erosion in Elim destroyed a local road and exposed the city's septic tanks and main water line. Shishmaref experienced some loss of sand, though recently constructed ripraps spared the area from significant damage.[47] Most affected areas had damage to power poles, with only coastal regions sustaining structural impacts. Losses throughout the state was conservatively estimated at $20 million.[6]
In the aftermath of the storm, on November 16, President George W. Bush signed a disaster declaration for the Bering Strait Regional Education Attendance Area and the Northwest Arctic Borough. Funding from the Federal Emergency Management Agency was made available to residents in these areas as well as the city of Mekoryuk.[48] Public assistance teams were deployed to Nome and Unalakleet on November 19 to establish a base of operations for relief and assess the impact of the storm. Visits to smaller communities throughout the affected region were planned as well.[49] At the end of November, the disaster declaration expanded to include Chevak, the Pribilof Islands Regional Education Attendance Areas, and communities along the Lower Kuskokwim and Lower Yukon rivers.[50]
See also
[edit]- Other tropical cyclones named Ma-on
- Other tropical cyclones named Rolly
- Tropical cyclones in 2004
- Other typhoons that struck Japan during the 2004 season:
- 2011 Bering Sea superstorm
- Typhoon Wipha (2013) – a typhoon which hit the same areas as Ma-on
- Typhoon Phanfone (2014) – another typhoon which affected the Japanese Grand Prix
- Typhoon Hagibis (2019) – a powerful typhoon which also struck eastern Japan, disrupting both the Japanese Grand Prix and the Rugby World Cup fifteen years later
References
[edit]- ^ a b c d e f g h i j Kevin Boyle and Huang Chunliang (February 17, 2005). "Super Typhoon Ma-on". Monthly Global Tropical Cyclone Summary: October 2004 (Report). Typhoon 2000. Retrieved July 14, 2014.
- ^ a b c d e f g (in Japanese) "台風0422号(0422 Ma-on)" (PDF). Japan Meteorological Agency. 2005. Retrieved July 14, 2014.
- ^ a b c d e "Super Typhoon 26W (Ma-on) Best Track" (.TXT). Joint Typhoon Warning Center. United States Navy. 2005. Retrieved July 17, 2014.
- ^ Gary Hufford and James Partain (2005). Climate Change and Short-Term Forecasting for Alaskan Northern Coasts (PDF) (Report). American Meteorological Society. Retrieved July 14, 2014.
- ^ C. Larsen, D. E. Atkinson, J. Walsh, J. Arnott, and K. Lingaas (2006). "Dynamical Development of the Bering/Chukchi Sea Storm, October, 2004". AGU Fall Meeting Abstracts. 2006. National Aeronautics and Space Administration: A21A–0827. Bibcode:2006AGUFM.A21A0827L. Retrieved July 15, 2014.
{{cite journal}}
: CS1 maint: multiple names: authors list (link) - ^ a b c d e f National Weather Service Office in Fairbanks, Alaska (2005). "Alaska Event Report: High Wind". National Climatic Data Center. National Oceanic and Atmospheric Administration. Retrieved July 14, 2014.
- ^ Katherine A. Pingree-Shippee, Norman J. Shippee, David E. Atkinson (2012). "Overview of Bering/Chukchi Sea Wave States for Selected Severe Storms" (PDF). University of Alaska Fairbanks. Retrieved July 15, 2014.
{{cite web}}
: CS1 maint: multiple names: authors list (link) - ^ "Typhoon Ma-on moves north, may strike Honshu Saturday". Tokyo, Japan. Japan Economic Newswire. October 8, 2004. p. 8. – via Lexis Nexis (subscription required)
- ^ "Strongest typhoon in decade set to strike Kanto". Tokyo, Japan. Japan Economic Newswire. October 9, 2004. – via Lexis Nexis (subscription required)
- ^ a b Mari Murayama and Iain Wilson (October 9, 2004). "Typhoon Ma-on Reaches Central Japan; Flights Canceled (Update2)". Bloomberg News. Retrieved July 18, 2014.
- ^ a b c "2 dead, 6 missing as Typhoon Ma-on floods Tokyo, vicinity". Tokyo, Japan. Japan Economic Newswire. October 9, 2014. – via Lexis Nexis (subscription required)
- ^ a b (in Japanese) "気象災害報告 (2004-936-21)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 24, 2014.
- ^ a b "Typhoon Ma-on lashes Tokyo". Australian Broadcasting Corporation. Agence France-Presse. October 9, 2004. Retrieved July 18, 2014.
- ^ "Play suspended at Japan Open tennis". Tokyo, Japan. Associated Press. October 9, 2004. – via Lexis Nexis (subscription required)
- ^ a b c Wataru Mashiko (2006). "High-resolution simulation of wind structure in the inner-core of Typhoon Ma-on (2004) and sensitivity experiments of horizontal resolution" (PDF). Japan Meteorological Agency: 1–2. Retrieved July 14, 2014.
{{cite journal}}
: Cite journal requires|journal=
(help) - ^ a b Yasou Okuda, Yukio Tamura, Hiroaki Nishimura, Hitomitsu Kikitsu, and Hisashi Okada (2005). "High Wind Damage to Buildings Caused by Typhoon in 2004" (PDF). United States–Japan Natural Resources Panel. Public Works Research Institute. Retrieved July 14, 2014.
{{cite journal}}
: CS1 maint: multiple names: authors list (link) - ^ Joo-Hong Kim, Chang-Hoi Ho, and Chung-Hsiung Sui (July 28, 2005). "Circulation features associated with the record-breaking typhoon landfall on Japan in 2004". Geophysical Research Letters. 32 (14): 2. Bibcode:2005GeoRL..3214713K. doi:10.1029/2005GL022494.
{{cite journal}}
: CS1 maint: multiple names: authors list (link) - ^ Wataru Mashiko (2008). "Formation Mechanism of a Low-Level Jet during the Passage of Typhoon Ma-on (2004) over the Southern Kanto District" (PDF). Journal of the Meteorological Society of Japan. 86 (1). Japan Meteorological Agency: 183–202. Bibcode:2008JMeSJ..86..183M. doi:10.2151/jmsj.86.183.
- ^ "Precipitation Summary". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 14, 2014.
- ^ a b (in Japanese) "気象災害報告 (2004-670-15)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 24, 2014.
- ^ a b (in Japanese) "気象災害報告 (2004-648-10)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 21, 2014.
- ^ (in Japanese) "気象災害報告 (2004-610-16)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 19, 2014.
- ^ (in Japanese) "気象災害報告 (2004-584-20)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 19, 2014.
- ^ (in Japanese) "気象災害報告 (2004-590-08)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 19, 2014.
- ^ (in Japanese) "気象災害報告 (2004-780-13)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 24, 2014.
- ^ (in Japanese) "気象災害報告 (2004-595-17)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 19, 2014.
- ^ "Strongest typhoon in 10 years to hit Japan". Tokyo, Japan. Deutsche Presse-Agentur. October 9, 2004. – via Lexis Nexis (subscription required)
- ^ (in Japanese) "気象災害報告 (2004-624-17)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 20, 2014.
- ^ (in Japanese) "気象災害報告 (2004-626-11)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 20, 2014.
- ^ (in Japanese) "気象災害報告 (2004-629-10)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 20, 2014.
- ^ (in Japanese) "気象災害報告 (2004-638-08)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 21, 2014.
- ^ (in Japanese) "気象災害報告 (2004-636-15)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 21, 2014.
- ^ (in Japanese) "気象災害報告 (2004-656-17)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 21, 2014.
- ^ (in Japanese) "気象災害報告 (2004-662-12)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 24, 2014.
- ^ (in Japanese) "気象災害報告 (2004-582-26)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 19, 2014.
- ^ (in Japanese) "気象災害報告 (2004-575-11)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 19, 2014.
- ^ (in Japanese) "気象災害報告 (2004-632-23)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 21, 2014.
- ^ (in Japanese) "気象災害報告 (2004-651-15)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 21, 2014.
- ^ (in Japanese) "気象災害報告 (2004-604-24)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 19, 2014.
- ^ (in Japanese) "気象災害報告 (2004-741-15)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 24, 2014.
- ^ (in Japanese) "気象災害報告 (2004-615-24)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 20, 2014.
- ^ (in Japanese) "気象災害報告 (2004-777-07)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 24, 2014.
- ^ (in Japanese) "気象災害報告 (2004-588-16)". Digital Typhoon. National Institute of Informatics. 2004. Retrieved July 19, 2014.
- ^ a b (in Japanese) "台風200422号 (MA-ON) – 災害情報". Digital Typhoon. National Institute of Informatics. 2011. Retrieved July 14, 2014.
- ^ OECD Studies in Risk Management: Japan Floods (PDF) (Report). Organisation for Economic Co-operation and Development. 2006. p. 9. Retrieved July 14, 2014.
- ^ Raymond S. Chapman, Sung-Chan Kim, and David J. Mark (October 2009). Storm-Induced Water Level Prediction Study for the Western Coast of Alaska (PDF) (Report). United States Army Corps of Engineers. p. 7. Retrieved July 15, 2014.
{{cite report}}
: CS1 maint: multiple names: authors list (link) - ^ a b c "Powerful Bering Sea storm hits Nome". Anchorage, Alaska. Associated Press. October 20, 2004. – via Lexis Nexis (subscription required)
- ^ "Federal Disaster Funds Ordered For Alaska To Aid State And Local Government Storm Recovery". Federal Emergency Management Agency. Government of the United States. November 16, 2004. Retrieved July 15, 2014.
- ^ "Joint State/Federal Assistance Teams Deploy to Nome and Unalakleet". Federal Emergency Management Agency. Government of the United States. November 19, 2004. Retrieved July 15, 2014.
- ^ "Additional Alaska Communities Designated For Public Assistance". Federal Emergency Management Agency. Government of the United States. November 30, 2004. Retrieved July 15, 2014.